The solution by that link doesn't cancel the actual HTTP request sent. It just raises an error. That's where 'cancellable-fetch' lib comes into play.

And 'promise-timeout' lib I've added actually uses Promise.race approach you mentioned. The only diff is it clears timeout if the request is successful or any other error happens.
In React native a non-cleared timeout can trigger warnings which look not really elegant... But for sure this can be easily implemented manually but why?

'uuid' lib was needed for identifying the HTTP request to cancel although here I agree it can be just replaced by a simple counter.

What you mention makes total sense. However, that would mean we should move away from the original implementation of the fetch API spec, included in ReactNative.

cancellable-fetch is a reimplementation. I'm not that convinced.

I'm personally not interested in turning this into a fully-featured http library, there are great solutions out there making a great job at this.

Let's keep the scope for now on being an abstraction of the fetch API. I'm reading that aborting http requests is already in the plans. Let's implement it when it's available for RN. Or is it already?